From e87ec75ad63327f146d71a476165660c8b62a1b4 Mon Sep 17 00:00:00 2001 From: "Richard M. Stallman" Date: Mon, 11 Dec 2006 02:34:51 +0000 Subject: [PATCH] (Font Lock Basics): Explain how nil for font-lock-defaults affects face menu. Explain how to make it non-nil without enabling any fontification. --- lispref/modes.texi | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/lispref/modes.texi b/lispref/modes.texi index 1462f1a2fdf..29c316d625d 100644 --- a/lispref/modes.texi +++ b/lispref/modes.texi @@ -2358,9 +2358,12 @@ Lock mode is enabled, to set all the other variables. @defvar font-lock-defaults This variable is set by major modes, as a buffer-local variable, to specify how to fontify text in that mode. It automatically becomes -buffer-local when you set it. If its value is @code{nil}, no -highlighting is performed. If non-@code{nil}, the value should look -like this: +buffer-local when you set it. If its value is @code{nil}, Font-Lock +mode does no highlighting, and you can use the @samp{Faces} menu +(under @samp{Edit} and then @samp{Text Properties} in the menu bar) to +assign faces explicitly to text in the buffer. + +If non-@code{nil}, the value should look like this: @example (@var{keywords} [@var{keywords-only} [@var{case-fold} @@ -2406,6 +2409,13 @@ fontification, aside from those you can control with the first five elements. @xref{Other Font Lock Variables}. @end defvar + If your mode fontifies text explicitly by adding +@code{font-lock-face} properties, it can specify @code{(nil t)} for +@code{font-lock-defaults} to turn off all automatic fontification. +However, this is not required; it is possible to fontify some things +using @code{font-lock-face} properties and set up automatic +fontification for other parts of the text. + @node Search-based Fontification @subsection Search-based Fontification -- 2.30.2